How to get the most from WANT

 You'll find that you usually search the same files. To search them 
 quickly, make a directory called myfiles and put your favorite files
 in this directory. Then enter the following line in your
 startup-sequence:

     ASSIGN aamyfiles: <path>myfiles 

 Notice the 'aa' preceeding the name. From WANT, click the VOLUMES
 button. The lists all the logical assigns made on your system, alpha- 
 betically. The 'aa' will insure this ASSIGN is at the top of the list,
 making it easier for you to find it.

 What can you put in this directory? RECENTS and INDEXES for a start. 
 Fred Fish listings, FAQs, articles, readmes, docs, and anything else 
 you might want to look through. This method eats up some disk space, 
 but saves you the hassle of hunting through directories to find files.

 When you search Fish listings, its a good idea to choose about 25 
 lines of leading and 5 lines of trailing context. You may adjust these
 numbers at any time. The more lines you select, the longer the search
 will take. (The filereader will take longer to load the file).

 Do you ever use FIND to locate a file on your hard drive? It's a 
 great program, but by necessity, slow. You can create a file 
 containing all the directories and files on your drive (or better yet,
 a partition) and then use WANT to search that file, rather than wait 
 for FIND. Here's how to do it:

 Let's assume you have created the ASSIGN outlined above, and want to 
 create a file that lists all the directories and files on your DH1: 
 partition. From the CLI type this:

   list >aamyfiles:dh1contents  DH1:* lformat "%F%N" ALL

 The drive light will come on for a while. When it turns off, the file 
 called dh1contents will be in the directory myfiles. Now you can use 
 WANT to search dh1contents. The search time should be less than one
 second on a 1200, and longer on a 7Mhz machine. This works on CDROMs
 and floppies also.

Using an Editor instead of a filereader
 
 You can select an editor instead of a filereader in the Tooltypes. 
 If your editor requires a stack to be set, WANT cannot do it for you.
 When the editor is called, it is passed the filename of a temporary 
 file lovcated in RAM:. This file is named GAWK_OUTPUTxxxxxxxx. When
 you save your file, always SAVE AS with a different filename and path,
 or the results of your editing will be lost.

A special note to the UN*X literate

 The two text entry fields will accept ANY UN*X-like search expressions. 
 Multiple expressions separated by the AND/OR gadget are allowed.
 Any expression that could be used by egrep is allowed. i.e. [AaBb], 
 all logical operators, and wildcards.

   Using UN*X Regular Expressions to search for more than two terms

 Enter the expression or multiple expressions like this:

     (word1)|(word2)|(word3)  etc.

 This will find word1 OR word2 OR word3. If you click the AND OR 
 gadget to AND, and enter another expression in the second text field, 
 the the search will AND the two expressions.
 
 Since WANT is designed to shield UN*X from the user, you may 
 encounted unpredictable results with multiple expressions. Grep and Gawk's 
 scripts are being assembled algorithmically in realtime. This presents 
 a large workload for the system. You CAN confuse the process with 
 overly complex expressions.